home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000402_news@columbia.edu _Tue Mar 11 14:22:05 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA02166
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 11 Mar 1997 14:22:03 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id OAA12006
for kermit.misc@watsun; Tue, 11 Mar 1997 14:22:02 -0500 (EST)
Path: news.columbia.edu!panix!news.eecs.umich.edu!news.radio.cz!newsbastard.radio.cz!news.radio.cz!CESspool!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!howland.erols.net!agate!news.Stanford.EDU!sep!stew
From: stew@sep.Stanford.EDU (Stewart Levin)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: FAST+FAST->Window slots 1 of 20
Date: 11 Mar 1997 19:13:41 GMT
Organization: Stanford Exploration Project
Lines: 34
Sender: stew@sep (Stewart Levin)
Distribution: world
Message-ID: <5g4at5$mte@nntp.Stanford.EDU>
References: <5fb64g$5fp@nntp.Stanford.EDU> <1997Mar7.152135.95352@cc.usu.edu>
NNTP-Posting-Host: oas.stanford.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:6736
In article <1997Mar7.152135.95352@cc.usu.edu>, jrd@cc.usu.edu (Joe Doupnik) writes:
|> In article <5fb64g$5fp@nntp.Stanford.EDU>, stew@taal.Stanford.EDU (Stewart Levin) writes:
|> > C-Kermit 6.0.192 on both ends (Linux and Sun OS 4.1.3)
|> > Binary file transfer mode
|> > FAST invoked on both ends before transfer
|> >
|> > SEND'ing a large file from the Sun to the PC produces
|> > 20 rapid packets followed by a much slower one-at-a-time
|> > crawl and the message that I am using 1 of 20 window slots.
|> > Cancelling the file takes 20 more packets to complete.
|> > This happens whether or not I use the SET BUFFERS 100000 100000
|> > command on both ends. Similarly with CAUTIOUS on both ends.
|> >
|> > Looks like it's the Linux end that's misbehaving.
|> > Have I overlooked something in the Using C-Kermit 2nd ed. chapter
|> > 12? Is there a patch I should retrieve?
|> -------------
|> You are forgetting that the comms channel may not be able to
|> cope. You don't say what that channel may be (or I've lost the scoop).
|> Not coping leads to lost packets, and that in turn causes Kermit to
|> slow down so losses are less likely.
|> Joe D.
Following the pointers and clarifications from this newsgroup, I've
had a chance to experiment. It appears that C-Kermit is working
exactly as advertised, it is just the quality of the phone connections
between my home and my office are on the average not very clean.
Every once in a while I do achieve a high throughput, however. Most
of the time I sustain about half the best speed. Once again, my
thanks to this group and, of course, to the authors of kermit and
its user's guides.
- Stew Levin
stew@sep.stanford.edu